Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1819

reference: 734-tree-1
name: 1819
tree-preservation-order: undefined
734-tpo-1
uprn
address-text
point: POINT (-0.978012 50.866231)
geometry: MULTIPOLYGON (((-0.977842 50.866213,-0.977849 50.866246,-0.977873 50.866277,-0.977910 50.866301,-0.977957 50.866317,-0.978010 50.866322,-0.978063 50.866317,-0.978111 50.866303,-0.978149 50.866279,-0.978174 50.866249,-0.978183 50.866216,-0.978175 50.866182,-0.978152 50.866152,-0.978114 50.866128,-0.978067 50.866112,-0.978015 50.866107,-0.977962 50.866111,-0.977914 50.866126,-0.977876 50.866150,-0.977851 50.866180,-0.977842 50.866213)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL